See how a minor change to your commit message style can make a difference.
git commit -m"<type>(<optional scope>): <description>" \ -m"<optional body>" \ -m"<optional footer>"
See how a minor change to your commit message style can make a difference.
git commit -m"<type>(<optional scope>): <description>" \ -m"<optional body>" \ -m"<optional footer>"
Authors: @h0j3n, @aniqfakhrul
Date: July 24, 2026
Certighost is an Active Directory Certificate Services (AD CS) vulnerability that allowed a low-privileged domain user to impersonate a Domain Controller and achieve domain compromise in the tested AD CS configuration. The issue was addressed in the July 2026 security updates.
The vulnerable path is an AD CS enrollment fallback known as a chase during directory-object resolution. By supplying request attributes such as cdc, an attacker could cause the Certification Authority (CA) to ask an attacker-controlled host for identity data belonging to a Domain Controller. The CA then used that data while issuing a certificate.
What happens to your apps if your phone breaks? Phones have become an essential part in our daily interactions with banks, social networks, entertainment, and what not. Losing or breaking a phone has never been more nervewrecking. Especially with apps that use local only storage with limited or no means of backup. Backing up data on Android is becoming harder, even for advanced users.
A decade ago, there were still viable options available for power users. Apps like Titanium Backup come to mind. But Android is being locked down tighter every year, because of financial regulations and trusted computing requirements. This mindset of turning phones into walled gardens where even a power user shall have no access is trickling down to forks such as LineageOS as well.
Modern versions of LineageOS, 18.1 as of the moment of writing, do no longer provide a practical way for applications to gain root. Backup applications such as Titanium Backup no longer work. T
| #ifndef DEMO_HARDWARE_ONLY | |
| #define DEMO_HARDWARE_ONLY 0 | |
| #endif | |
| #define WIN32_LEAN_AND_MEAN | |
| #include <windows.h> | |
| #include <dwmapi.h> | |
| #include <d3d11.h> | |
| #include <dxgi1_2.h> | |
| #include <stdio.h> |
A pattern for building personal knowledge bases using LLMs.
This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.
Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.
These settings will get you the best visuals for the cheapest cost. Turning the settings higher does not significantly improve the visual quality but it WILL significantly increase the performance cost. If you have a weaker GPU you may want to set things lower.